home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
AOL File Library: 4,401 to 4,500
/
aol-file-protocol-4400-4401-to-4500.zip
/
AOLDLs
/
PDA-Newton Development
/
ND Newt Development Environm
/
newt-devenv-31.sit
/
packages.txt
< prev
next >
Wrap
Text File
|
1995-08-11
|
7KB
|
158 lines
packages.txt
8/11/95
Newt 3.1
(c) 1995, S. Weyer, All Rights Reserved Worldwide.
weyer@netaxs.com
With Newt 3.1, it is possible to save packages directly on the Newton. For
this you need the NewtPack plug-in which is provided with the standard
release.
Configuration?
The NewtPack included with Newt 3.1 should work on ALL Newtons. For
older/original, pre-1.3 ROMs, non-upgraded OMP (Original MessagePads),
NewtPack must use a "small saving method" which limits the size of final
packages. You should still be able to create modest-sized (~30-40K)
packages. When NewtPack begins to save, the version/configuration appears
-- NewtPack appends "+S" to the version number if it is using this "small"
method.
NewtPack is relatively slow. However, since you can build and test your
applications in Newt, you do not need to create a package until toward the
end of your development process. There is a version of NewtPack available
to registered users that contains various amount of native (RISC) code. It
is currently ~20% faster than the regular version, and somewhat larger -- I
will continue to profile and improve performance.
If you used the older RUNewt mechanism, see "RUNewt" at end.
Use
When you install NewtPack, it does not appear in Extras since it is an
"autopart". When Newt starts up, it finds the NewtPack plug-in, and
automatically uses it to save your application, either via the Save button
or :saveApp. As your package saves, NewtPack displays the most recent slot
at bottom left, and current package size at bottom right.
The status bar shows progress (in bytes) toward a possible package size. Since
NewtPack can't compute an accurate size in advance, it defaults to 40K,
though you can give NewtPack a better hint -- so, don't worry if NewtPack
appears to terminate half-way through or keeps on going for awhile
(especially if you're copying platform functions or other large "constants").
You will hear a "funbeep" if it's successful and the progress box will
automatically disappear; or, you will hear an error beep, see a message, and
a close box should appear on the progress box.
If there is an existing package with the same "appSymbol", e.g., myApp:Newt,
NewtPack asks you to confirm removing the old package before proceeding. If an
error occurs during saving, you might try again after a fresh restart, in
case a heap problem was reported; otherwise, if you're creating an autopart
or using an installScript, look at the examples & docs again...
Manipulating Packages
If the package successfully saved and installed, it should be
indistinguishable from an NTK-created package, and you should be able to
use utilities that archive packages and manipulate Extras, e.g., NewtCase,
ScrollEx, etc. You may wish to obtain one of these, or at least a utility
that will allow you to scroll the "Remove Software" list -- newer system
updates from Apple have a utility called "Package Mover" that allows the
"Prefs:Memory:Remove Software" list to scroll. Let me know which work best
for you (or don't work) so that I can pass along this info.
In addition to beaming any NTK or Newt package to another Newton via a utility
like BeamPkg or ScrollEx, you can backup the package to your Mac or PC with
Newton Connection Kit. Once there, you can extract the package from the NCK
backup file with an Extract Package utility (and then copy to floppy, upload
somewhere or attach to email).
ExtractPackages 1.1 (for the Mac)
author: markus_fritze@hh2.maus.de; CIS: 100074,3560
ftp://ftp.amug.org/pub/newton/mac-only/extract-packages_1.1.sit.hqx
AOL: pack.sit (1.0?)
CIS:NEWTON: EXTRAC.SIT
eWorld:Newton:Utilities: ExtractPackage 1.1
ExtractPackage 1.1 (or 2.0?) (for Windows)
author: raf@rough.demon.co.uk
ftp://ftp.amug.org/pub/newton/dos-only/extrap2l.zip.hqx
AOL: extrap21.zip
CIS: EXTRAP.SIT
Some Windows users have experienced problems with Extract Package. One thing
to check is that you have msafinx.dll installed; this may be avail with
Visual Basic 3.0.
Please support authors of other utilities by sending words of
encouragement or money as appropriate.
Distribution
Of course, what you do with these packages is your own decision. If you plan
to distribute to others, I'd be glad to review designs and source and
beta-test, as time permits. Please include the following acknowledgment in
your "readme" (text file or online help):
This application created with the Newt Development Environment (Newt 3.1).
For further information, browse: http://www.netaxs.com/~weyer
or contact: weyer@netaxs.com.
Also, if you let me know the package location/URL, I can add your Newt-generated
package to the list on my web page: www.netaxs.com/~weyer/newton/releases.html
and tell others about it.
If you plan to sell your packages, I do not charge royalties -- it would be
appreciated if you registered Newt. Although I assume that Apple does not
have legal rights to information that your applications create, anything is
possible, so this situation could change; all disclaimers and caveats apply.
My view is that Apple will be well-rewarded by having additional development
tools available:
- many more software packages to make the platform attractive to users
- many more developers, many of whom upgrade to NTK tools and support
- wider choices of development features & platforms
- and, if enough of you register for Newt, I will be forced over a revenue
threshhold and have to start paying 1% royalties to Apple
Future
Performance. Now that NTK 1.5 is available, I will profile and compile
selected methods as native (RISC) code. There is a version available to
registered users that is ~20% faster, and I expect this to improve somewhat
(though not dramatically) over time.
Stability. NewtPack's package model is based on some earlier public info
(thanks to Dave Fedor, Matthew Faupel), plus some ViewFrame archaelogy and
a lot of trial-and-error and educated guesses. Although I think NewtPack is
robust and relatively complete, based on the several dozen examples that
I've tested, and packages that users have created (no bugs have been
reported), I will be more confident after further testing and/or if real
package info becomes available from Apple (I have been requesting & waiting
for ~2 years).
Completeness. NewtPack currently handles regular apps ("forms"), autoparts
and books; a future version will likely handle fonts, stores and other
objects/attributes.
RUNewt
I have removed the older, separate "RUNewt" mechanism & info.
(RUNewt was used before packages (pre- Newt 3.0) to save and run applications).
You can remove the "RUNewt:TKnollSys" package. If you are careful, you can
remove the "RUNewt:Apps:TKnollSys" soup, and the "RunNewtRun:TKnollSys"
System preference with a soup utility like StewPot.